Release 10.1A: OpenEdge Data Management:
Database Administration

Servers

Displays status information about OpenEdge servers running on the system.

Figure 19–12 shows a sample Servers Status display.

09/15/05 Status: Servers 14:07:47 Sv Pend. Cur. Max. Port No Pid Type Protocol Logins Users Users Users Num 0 4899 Login TCP 1 0 0 5 2402 1 22849 Auto TCP 1 0 1 5 1025 2 0 Inactive 0 0 0 0 0 3 0 Inactive 0 0 0 0 0 4 0 Inactive 0 0 0 0 0

Figure 19–12: PROMON Servers Status display

The display contains the following fields:

Type — The server type. Table 19–10 describes the possible types.

Table 19–10: Server types

State	Description
Broker	A broker process. A broker logs in clients and starts remote servers.
Auto	A server started automatically by the broker.
Manual	A server started manually (with the Manual Server (-m2) startup parameter) after the broker was started. You might start a server manually for debugging purposes, or on a system where a server cannot be started automatically.
Login	A secondary login broker. When a database network includes more than one protocol, a secondary login broker performs broker functions for the second protocol.
Inactive	Placeholder in the server table for servers that have not yet started.

Protocol — The communications protocol used by the server and its clients. TCP is the only valid value for this field.
Pend. Users — The number of users who have successfully connected to the broker, but have not completed a connection to a server.
Cur. Users — The number of users currently connect to a server.
Max. Users — The maximum number of users who can connect to a server.